Skip to main content
Check and provide your planning data

BETA This is a new service – your feedback will help us to improve it.

Back to dataset table
East Hampshire District Council

Tree

There is a problem

  • 1000 entries with tree-preservation-order field must match the reference field in the tree preservation order

1609

reference
541-tree-1
name
1609
tree-preservation-order

undefined

541-tpo-1
uprn
address-text
point
POINT (-1.023905 50.884127)
geometry
MULTIPOLYGON (((-1.023848 50.884121,-1.023851 50.884132,-1.023859 50.884143,-1.023871 50.884151,-1.023887 50.884156,-1.023905 50.884158,-1.023922 50.884156,-1.023938 50.884151,-1.023951 50.884143,-1.023959 50.884133,-1.023962 50.884122,-1.023960 50.884111,-1.023952 50.884101,-1.023939 50.884093,-1.023924 50.884088,-1.023906 50.884086,-1.023888 50.884087,-1.023873 50.884092,-1.023860 50.884100,-1.023851 50.884110,-1.023848 50.884121)))
notes
felled-date
entry-date
2026-08-06
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that affects this tree.

Example: TPO1

This diagram shows the relationship between the tree preservation order dataset and the tree dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree dataset.

How to improve East Hampshire District Council’s data

  1. Fix the errors indicated
  2. Use the check service to make sure the data meets the standard
  3. Publish the updated data on the endpoint URL